Skip to content

fix: bump @kunobi/mcp-installer to ^0.0.7 for Copilot CLI support - #7

Merged
emmanuelm41 merged 2 commits into
mainfrom
fix/bump-mcp-installer-copilot
May 27, 2026
Merged

fix: bump @kunobi/mcp-installer to ^0.0.7 for Copilot CLI support#7
emmanuelm41 merged 2 commits into
mainfrom
fix/bump-mcp-installer-copilot

Conversation

@chcmedeiros

Copy link
Copy Markdown
Member

Problem

npx @kunobi/mcp install does not offer GitHub Copilot CLI, even though @kunobi/mcp-installer@0.0.7 already added it to the CLIENTS list.

Root cause is a semver pin: this package declared "@kunobi/mcp-installer": "^0.0.6". For 0.0.x versions the caret does not mean "0.0.6 or newer" — it resolves to exactly 0.0.6. So the dependency tree locked to installer 0.0.6 (no Copilot) and never picked up 0.0.7.

Verified by resolving the tree of the published @kunobi/mcp@0.0.15:

@kunobi/mcp@0.0.15
└── @kunobi/mcp-installer@0.0.6   ← Copilot absent

Fix

Bump the dependency to ^0.0.7 so the installer build that includes the Copilot CLI client is used. pnpm-lock.yaml regenerated to match; pnpm install --frozen-lockfile (what CI runs) passes.

A new @kunobi/mcp release is required for this to reach users via npx.

Files

  • package.json@kunobi/mcp-installer ^0.0.6^0.0.7
  • pnpm-lock.yaml — regenerated (resolves 0.0.7)

chcmedeiros and others added 2 commits May 27, 2026 15:02
^0.0.6 pins the installer to exactly 0.0.6 (caret semantics on 0.0.x), so the GitHub Copilot CLI client added in installer 0.0.7 never reached `npx @kunobi/mcp install`.
The shared CI image enforces a 24h supply-chain age policy, which blocks
this PR from consuming @kunobi/mcp-installer@0.0.7 (published <24h ago by
us). Override locally to 0 since we control these packages ourselves.
@emmanuelm41
emmanuelm41 merged commit 0027bdf into main May 27, 2026
2 checks passed
emmanuelm41 pushed a commit that referenced this pull request May 27, 2026
Replaces the blanket `minimumReleaseAge: 0` from #7 with
`minimumReleaseAgeExclude: ['@kunobi/*']` so the 24h supply-chain age
gate from the CI image still applies to every third-party dependency
(zod, @modelcontextprotocol/sdk, rollup, biome, vitest, …) and only
in-house packages we publish ourselves bypass it.
emmanuelm41 added a commit that referenced this pull request May 27, 2026
Replaces the blanket `minimumReleaseAge: 0` from #7 with
`minimumReleaseAgeExclude: ['@kunobi/*']` so the 24h supply-chain age
gate from the CI image still applies to every third-party dependency
(zod, @modelcontextprotocol/sdk, rollup, biome, vitest, …) and only
in-house packages we publish ourselves bypass it.

Co-authored-by: emmanuelm41 <emmanuel@zondax.ch>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants